I'd suggest having a function that converts the old tags to the new one and immediately change the "railway_train_protection_rank" and "railway_train_protection_rendered" functions to completely use the new system, so if everything got re-tagged, we can just easily remove the helper function.

Hi!
I am not sure we really need the "railway_train_protection_rank", I left it for compatibility in the transition phase. If it could be removed, and I think so because "rank" is only used for ordering the SELECT results, then "railway_train_protection_rendered" would basically coincide with the proposed converting function.
I'll have a look into it.

EDIT: yes, we can do without. "railway_train_protection_rendered" is now the only place to contain the handling of tags.

I meant having railway_train_protection_rendered to already contain the code for all new tags and for backwards compatibility have another function to convert the old tags to the new one.

I generally agree, but…

We must finish the definition of the tagging first. I very much like the idea to just "ban" the addition of new systems using the old scheme. Technically, i.e. adapting the code, you can try everything out. But please don't change other peoples tagging just for experiments. Doing it on your own is IMHO fine, although I would prefer that you keep the old tagging as well until things are approved.

While I have been slacking for the proposal I would welcome any help getting it up to vote. But the contents and transitions should be mostly discussed on the wiki, and use GH only for the technical adaption.

That's why I suggested the conversion function. So the transition in ORM is seamless regardless of when the new tagging is applied.

Anyways, I volunteer myself too for retagging all Italy if needed.
Maybe is asking too much but why not dotted lines (like multiple gauges) if there are more than one train protection systems?

Hi!

Just a few comments, since apparently the development ran again into the issue that this PR is designed to solve.

We must finish the definition of the tagging first.

Could we limit the scope on "define a new tag for the signalling systems currently implemented in ORM"? Otherwise it's very much a neverending task. Who is actively working on the definition, anyways?

I very much like the idea to just "ban" the addition of new systems using the old scheme.

My feeling is that what is displayed in ORM gets tagged, the rest does not exist. See SCMT, things start to get tagged when someone does a PR here, not when something is added to the Wiki. Sorry but if that was the real process we would have all the world tagged.

Technically, i.e. adapting the code, you can try everything out. But please don't change other peoples tagging just for experiments.

In OSM I have changed nothing, I have ADDED tags for this test. I don't see a problem for ORM to specify what can be displayed or not, people will still be able to tag whatever they want, how they want. See for example construction:railway and railway:construction, duplicates are already everywhere, as a rendering software you are free choose what to display.

I would prefer that you keep the old tagging as well until things are approved.

Sorry if I ask, but I completely don't understand how this approval works, namely who exactly is involved and where the process takes place. I tried to jump in, the wiki discussion is half dead, here the activity is minimal, is there a mailing list or something? I'm really worried that we may wait for something that is not coming.

What I have seen so far is that something is not tagged, one starts tagging it and proposes a PR here, and suddenly things appear on maps and others start tagging because they see it working. Before my PR on SCMT the tagging coverage was a couple of lines across all Italy, after the PR it was the entire country in a matter of a few months (and it was not just me).
I think this "can do" approach could work for the new tagging, as long as we don't delete any other tag in OSM.

My feeling is that what is displayed in ORM gets tagged, the rest does not exist. See SCMT, things start to get tagged when someone does a PR here, not when something is added to the Wiki. Sorry but if that was the real process we would have all the world tagged.

Sorry if I ask, but I completely don't understand how this approval works, namely who exactly is involved and where the process takes place. I tried to jump in, the wiki discussion is half dead, here the activity is minimal, is there a mailing list or something? I'm really worried that we may wait for something that is not coming.

What I have seen so far is that something is not tagged, one starts tagging it and proposes a PR here, and suddenly things appear on maps and others start tagging because they see it working. Before my PR on SCMT the tagging coverage was a couple of lines across all Italy, after the PR it was the entire country in a matter of a few months (and it was not just me). I think this "can do" approach could work for the new tagging, as long as we don't delete any other tag in OSM.

Agree with @davide84 here, add more Train Protection tags and the rest wil come eventually. I want to add more but the color-scheme will be a mess.

So one of the first things needed will be a regional / continental grouped lists of (national) train protection systems with accompanying colors.

Sorry if I ask, but I completely don't understand how this approval works, namely who exactly is involved and where the process takes place. I tried to jump in, the wiki discussion is half dead, here the activity is minimal, is there a mailing list or something? I'm really worried that we may wait for something that is not coming.

The current status of the proposal is just a draft, so not intended to be seen yet. Once he has finished writing the proposal wiki page he can officially propose it and publish it on the forum and mailing list so people see it and will comment.

You can read more about the process in the wiki.